-
Notifications
You must be signed in to change notification settings - Fork 253
Check that string probe port match container port #457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Parameters: params.ParamDescs, | ||
ParseAndValidateParams: params.ParseAndValidate, | ||
Instantiate: params.WrapInstantiateFunc(func(_ params.Params) (check.Func, error) { | ||
return util.PerNonInitContainerCheck(func(container *v1.Container) []diagnostic.Diagnostic { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be great if you extract this to a named function and add unit tests to check all code paths.
@jouve You need to regenerate files |
I'll update this PR soon :) |
@jouve ping |
@jouve Could you rebase? I think we can make it into next release |
Closing due to lack of activity |
implementation of #455
if a probe port is a string and the string is not of number (like
"1234"
) and the string is not in the container ports (ie. ` ports[].name), then raise a diagnostic message.while the resource it accepted by kube currently, the liveness/readiness/startup will fail anyway, so added to default checks.